Add descriptive 403 for /server endpoint#1497
Merged
jokob-sk merged 1 commit intonetalertx:mainfrom Feb 8, 2026
Merged
Conversation
Contributor
📝 WalkthroughWalkthroughThe pull request adds a custom 403 Forbidden error page and configures nginx to serve it when clients attempt to access the /server endpoint without proper authorization. This includes a new HTML file and an nginx configuration directive. Changes
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
No actionable comments were generated in the recent review. 🎉 Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A new 403 page describes the issue faced in #1496, which is intended operation. However, the previous standard Nginx 403 message was too generic and did not give the user any further information about how to proceed when faced with a 403 from the internal

/serverproxy. This 403 page should fix that problem.Summary by CodeRabbit